Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6df9e18e87fafa2f209ef9bd748bfe43d3f32b7229b4cd6f4c64910087b79eb0

Tx prefix hash: 5671051a94feed95ba1a92580b780b42527c2c770ff8eb5914c8c2757bda5139
Tx public key: 5c282dc8c153e193ca015e404368d6448b881c07b2e15ef2e3babdd4b492ddc6
Timestamp: 1725818001 Timestamp [UCT]: 2024-09-08 17:53:21 Age [y:d:h:m:s]: 00:282:14:27:38
Block: 1105789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201743 RingCT/type: yes/0
Extra: 015c282dc8c153e193ca015e404368d6448b881c07b2e15ef2e3babdd4b492ddc602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 341776f46b44cae659578d5e1da0f3a0807d46250d455c4937473c002cdca71b 0.600000000000 1583250 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": 1105799, "vin": [ { "gen": { "height": 1105789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "341776f46b44cae659578d5e1da0f3a0807d46250d455c4937473c002cdca71b" } } ], "extra": [ 1, 92, 40, 45, 200, 193, 83, 225, 147, 202, 1, 94, 64, 67, 104, 214, 68, 139, 136, 28, 7, 178, 225, 94, 242, 227, 186, 189, 212, 180, 146, 221, 198, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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