Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28090df1147c9be6f66802e5cfb7687390c72668331e80cc7437924c1a96f981

Tx prefix hash: e8dd557b68d79316aede3d2a9f7ca32d598e107e18a2be26818c59d273c13afd
Tx public key: db203e57735daacf5e11f3732860ed5e3614c60280baafd3a96ead3063d6d3d0
Timestamp: 1725129907 Timestamp [UCT]: 2024-08-31 18:45:07 Age [y:d:h:m:s]: 01:080:21:20:42
Block: 1100081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316255 RingCT/type: yes/0
Extra: 01db203e57735daacf5e11f3732860ed5e3614c60280baafd3a96ead3063d6d3d0021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1f1d4736b9f0d4e996ee0efb3304c0650d1c8a81fb9e62f421d2eb862c79995 0.600000000000 1576054 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": 1100091, "vin": [ { "gen": { "height": 1100081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f1d4736b9f0d4e996ee0efb3304c0650d1c8a81fb9e62f421d2eb862c79995" } } ], "extra": [ 1, 219, 32, 62, 87, 115, 93, 170, 207, 94, 17, 243, 115, 40, 96, 237, 94, 54, 20, 198, 2, 128, 186, 175, 211, 169, 110, 173, 48, 99, 214, 211, 208, 2, 17, 0, 0, 0, 3, 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