Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80a27ed741e326b5dacb1a93ae0223545f7ed255020f5b9434f448aa908a6afb

Tx prefix hash: be3411fbf4529c425ef4bcd1e4581262ae50c2093ea45eb377ecea8e9fbf070f
Tx public key: 4dfcff21f85de4140b0a28b98e55c5c2f2ee9398df6067d9fa31b58942c8ef27
Timestamp: 1717666209 Timestamp [UCT]: 2024-06-06 09:30:09 Age [y:d:h:m:s]: 00:292:20:58:50
Block: 1038215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209279 RingCT/type: yes/0
Extra: 014dfcff21f85de4140b0a28b98e55c5c2f2ee9398df6067d9fa31b58942c8ef270211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b707bbd490a787264242f394267bf46cff1a9b4e152e392d4bdb252229a8045c 0.600000000000 1506776 of 15

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": 1038225, "vin": [ { "gen": { "height": 1038215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b707bbd490a787264242f394267bf46cff1a9b4e152e392d4bdb252229a8045c" } } ], "extra": [ 1, 77, 252, 255, 33, 248, 93, 228, 20, 11, 10, 40, 185, 142, 85, 197, 194, 242, 238, 147, 152, 223, 96, 103, 217, 250, 49, 181, 137, 66, 200, 239, 39, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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