Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1500843cf5b617d19b8bf2f6ffffee5990965cf269c1d98c1ae59de78ff04f1f

Tx prefix hash: 2d600a4e165733f624b1ab3259f6f530fbb0f7096c1e69076fd515aed77e6488
Tx public key: 7ed2a410a604b4fde99edd805fcd9a18bd5f8e634cdf796186f02178153e1aec
Timestamp: 1718750232 Timestamp [UCT]: 2024-06-18 22:37:12 Age [y:d:h:m:s]: 00:348:11:25:03
Block: 1047192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249074 RingCT/type: yes/0
Extra: 017ed2a410a604b4fde99edd805fcd9a18bd5f8e634cdf796186f02178153e1aec0211000000020bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8148c52e00340d0722ebe935347fe2d3fded927c2e5ccdf3e4f6e19e2a27f204 0.600000000000 1517011 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": 1047202, "vin": [ { "gen": { "height": 1047192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8148c52e00340d0722ebe935347fe2d3fded927c2e5ccdf3e4f6e19e2a27f204" } } ], "extra": [ 1, 126, 210, 164, 16, 166, 4, 180, 253, 233, 158, 221, 128, 95, 205, 154, 24, 189, 95, 142, 99, 76, 223, 121, 97, 134, 240, 33, 120, 21, 62, 26, 236, 2, 17, 0, 0, 0, 2, 11, 186, 22, 215, 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