Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b1a7c1d2e0888b7cf1fa81dfb852a0c97ce0f1e27ec4d50caddad0598bda3f7

Tx prefix hash: 3977a40e33f0afbed596902956923a708facd2581eb3e8f88cb82754f9d81b63
Tx public key: 5a3c31e5af38545f5d0b6194ce4b7ce89e418e7804d461f5fb6a1cb8246b7666
Timestamp: 1733961374 Timestamp [UCT]: 2024-12-11 23:56:14 Age [y:d:h:m:s]: 00:107:18:01:26
Block: 1173216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76783 RingCT/type: yes/0
Extra: 015a3c31e5af38545f5d0b6194ce4b7ce89e418e7804d461f5fb6a1cb8246b7666021100000002c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab024a424103f514f2f91622e473072c823165c042c7a76a8ce96852091372dc 0.600000000000 1659213 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": 1173226, "vin": [ { "gen": { "height": 1173216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab024a424103f514f2f91622e473072c823165c042c7a76a8ce96852091372dc" } } ], "extra": [ 1, 90, 60, 49, 229, 175, 56, 84, 95, 93, 11, 97, 148, 206, 75, 124, 232, 158, 65, 142, 120, 4, 212, 97, 245, 251, 106, 28, 184, 36, 107, 118, 102, 2, 17, 0, 0, 0, 2, 199, 202, 20, 193, 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