Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b763bc96283e05ee8b78fff271397702fb8079bdcdaf551c4a11bb4faaef196

Tx prefix hash: 26a5558ae699c02348acb0581c282e89c434e17e702ba8575c2435c3e49a0259
Tx public key: b8cac7627f30f794cdaf7b1acac12efafa83f3df8d84d70407e50557056e36f5
Timestamp: 1632788431 Timestamp [UCT]: 2021-09-28 00:20:31 Age [y:d:h:m:s]: 03:062:04:08:43
Block: 342161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 821150 RingCT/type: yes/0
Extra: 01b8cac7627f30f794cdaf7b1acac12efafa83f3df8d84d70407e50557056e36f502110000000bf60c5d7e000000000000000000

1 output(s) for total of 45.110641261000 dcy

stealth address amount amount idx
00: 396310661c2e4d9ef7e16713dbbf39ea00e313e02d5302cb5f07afa281090a64 45.110641261000 702723 of 0

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": 342171, "vin": [ { "gen": { "height": 342161 } } ], "vout": [ { "amount": 45110641261, "target": { "key": "396310661c2e4d9ef7e16713dbbf39ea00e313e02d5302cb5f07afa281090a64" } } ], "extra": [ 1, 184, 202, 199, 98, 127, 48, 247, 148, 205, 175, 123, 26, 202, 193, 46, 250, 250, 131, 243, 223, 141, 132, 215, 4, 7, 229, 5, 87, 5, 110, 54, 245, 2, 17, 0, 0, 0, 11, 246, 12, 93, 126, 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