Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd02970d2d7bf112163fc120054e04f1be6ac10a09e4fe4d5587ee72bbca31da

Tx prefix hash: dfbb6e3511ee8877c067a907149104e4d0c2cc3dccc47246b11f8e8869704a2c
Tx public key: 4c4ec17b78e15ffd518c55199672a90d585cd9fbd791ae82393ea9d12f27d270
Timestamp: 1704600411 Timestamp [UCT]: 2024-01-07 04:06:51 Age [y:d:h:m:s]: 01:093:14:33:00
Block: 929863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328016 RingCT/type: yes/0
Extra: 014c4ec17b78e15ffd518c55199672a90d585cd9fbd791ae82393ea9d12f27d27002110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65686c7289a57eb5a73eb724d41babcdceedc5279c95f8e200fbcc041eaf1f8a 0.600000000000 1387739 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": 929873, "vin": [ { "gen": { "height": 929863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65686c7289a57eb5a73eb724d41babcdceedc5279c95f8e200fbcc041eaf1f8a" } } ], "extra": [ 1, 76, 78, 193, 123, 120, 225, 95, 253, 81, 140, 85, 25, 150, 114, 169, 13, 88, 92, 217, 251, 215, 145, 174, 130, 57, 62, 169, 209, 47, 39, 210, 112, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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