Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 35e32e145c0febb24888bb123e3f98a78695532d8503b56ae02f80d5e7a46628

Tx prefix hash: ed7b8443ce0ac8b1dfd6ad934dae93cf2195313f6ab4e512dbaf76ee633960f2
Tx public key: f3026bd9cd3453efbaa1ed34940a8ef491ac3d210b1a139f6aa6b24d5755987d
Timestamp: 1677915070 Timestamp [UCT]: 2023-03-04 07:31:10 Age [y:d:h:m:s]: 02:080:06:00:00
Block: 709538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 578963 RingCT/type: yes/0
Extra: 01f3026bd9cd3453efbaa1ed34940a8ef491ac3d210b1a139f6aa6b24d5755987d021100000002e6d27f9c000000000000000000

1 output(s) for total of 2.735306277000 dcy

stealth address amount amount idx
00: fdfeca327c1910e452a7cd6206e1baa976dcb1128c3628cd51e5a4cc62f03b9c 2.735306277000 1153529 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 709548, "vin": [ { "gen": { "height": 709538 } } ], "vout": [ { "amount": 2735306277, "target": { "key": "fdfeca327c1910e452a7cd6206e1baa976dcb1128c3628cd51e5a4cc62f03b9c" } } ], "extra": [ 1, 243, 2, 107, 217, 205, 52, 83, 239, 186, 161, 237, 52, 148, 10, 142, 244, 145, 172, 61, 33, 11, 26, 19, 159, 106, 166, 178, 77, 87, 85, 152, 125, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8