Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34d072dc4d7875b564386906000303e618d4b584db3e60ecf649c2700d7fe072

Tx prefix hash: ca6c68dd5363ac4dafd4f42a36d7d570207ec2576f24fbea5a2c1a7eedfac0b8
Tx public key: 44bf4eb0e21880fb326d8bee3d55d03549495d64dd10d0f895d125a8cd6c6201
Timestamp: 1715879942 Timestamp [UCT]: 2024-05-16 17:19:02 Age [y:d:h:m:s]: 00:328:01:14:34
Block: 1023394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234484 RingCT/type: yes/0
Extra: 0144bf4eb0e21880fb326d8bee3d55d03549495d64dd10d0f895d125a8cd6c620102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa67b2fbc3be928b1bf0f4f0ad8778a190b8172fc17f4691a17fea69349b64ee 0.600000000000 1488341 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": 1023404, "vin": [ { "gen": { "height": 1023394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa67b2fbc3be928b1bf0f4f0ad8778a190b8172fc17f4691a17fea69349b64ee" } } ], "extra": [ 1, 68, 191, 78, 176, 226, 24, 128, 251, 50, 109, 139, 238, 61, 85, 208, 53, 73, 73, 93, 100, 221, 16, 208, 248, 149, 209, 37, 168, 205, 108, 98, 1, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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