Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 583c10f2e94b9060f5e4280746e45fd594ca4c73eb608bda80f831e3da886a0a

Tx prefix hash: 6179dc82f58ec9a0ad426e2e083fcedf95141b44cbb1b694ee3c2cf0efae616c
Tx public key: fb30d22f84963c5e0aca69fed8ccff464f681be9c9772aad2b6af31c78f69d9b
Timestamp: 1729179119 Timestamp [UCT]: 2024-10-17 15:31:59 Age [y:d:h:m:s]: 01:021:13:16:37
Block: 1133652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273767 RingCT/type: yes/0
Extra: 01fb30d22f84963c5e0aca69fed8ccff464f681be9c9772aad2b6af31c78f69d9b02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27e3fbb55518e8df91a0956cc8de8943cf0166b4db52130a46e98b7d67a67af4 0.600000000000 1616831 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": 1133662, "vin": [ { "gen": { "height": 1133652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27e3fbb55518e8df91a0956cc8de8943cf0166b4db52130a46e98b7d67a67af4" } } ], "extra": [ 1, 251, 48, 210, 47, 132, 150, 60, 94, 10, 202, 105, 254, 216, 204, 255, 70, 79, 104, 27, 233, 201, 119, 42, 173, 43, 106, 243, 28, 120, 246, 157, 155, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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