Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87cb4b9104ac01cfc4d9605e1996529bc4d20459a34c4c906be8709f6bcbde26

Tx prefix hash: e95d385c5f522f7cdf3f1f91ff423dde35120b19725599bb27f7684178496995
Tx public key: aab4f7faf8f99260788660bac501f874c069e2d3953007d3859ba86d5fd2ff3d
Timestamp: 1577656954 Timestamp [UCT]: 2019-12-29 22:02:34 Age [y:d:h:m:s]: 05:002:21:36:40
Block: 34573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152076 RingCT/type: yes/0
Extra: 01aab4f7faf8f99260788660bac501f874c069e2d3953007d3859ba86d5fd2ff3d02110000000a8a2ee0d9000000000000000000

1 output(s) for total of 471.461414276000 dcy

stealth address amount amount idx
00: 2adf3a3505a6a37ab5c9eadf931fcbbe65e65ebfa36a4b17091ef48a4ddebef5 471.461414276000 58211 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": 34583, "vin": [ { "gen": { "height": 34573 } } ], "vout": [ { "amount": 471461414276, "target": { "key": "2adf3a3505a6a37ab5c9eadf931fcbbe65e65ebfa36a4b17091ef48a4ddebef5" } } ], "extra": [ 1, 170, 180, 247, 250, 248, 249, 146, 96, 120, 134, 96, 186, 197, 1, 248, 116, 192, 105, 226, 211, 149, 48, 7, 211, 133, 155, 168, 109, 95, 210, 255, 61, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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