Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7b2ecf91db82c965f83fe7ccad66de50cc2e037119c2b6f36e2b18d6b6a7b6d

Tx prefix hash: 6151326fff1f330bb4738b46bc49a6db76dfcc31f772a53e2c0303b7fe7d504b
Tx public key: a9150c0d02d388ba32a7e331d221af7031ab2bfb4f37a058498146dff26b1caa
Timestamp: 1703417176 Timestamp [UCT]: 2023-12-24 11:26:16 Age [y:d:h:m:s]: 01:101:10:25:20
Block: 920083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333594 RingCT/type: yes/0
Extra: 01a9150c0d02d388ba32a7e331d221af7031ab2bfb4f37a058498146dff26b1caa02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efd69c0009a99fb994164fc598802dad30b80700b952e3553b4ad187d7415a53 0.600000000000 1377761 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": 920093, "vin": [ { "gen": { "height": 920083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efd69c0009a99fb994164fc598802dad30b80700b952e3553b4ad187d7415a53" } } ], "extra": [ 1, 169, 21, 12, 13, 2, 211, 136, 186, 50, 167, 227, 49, 210, 33, 175, 112, 49, 171, 43, 251, 79, 55, 160, 88, 73, 129, 70, 223, 242, 107, 28, 170, 2, 17, 0, 0, 0, 6, 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