Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0410221d5a3f77f6abe43f3dbacf0396cee35fc107d00f414759c15f5737277

Tx prefix hash: e01b7901bb60e656feef45a6694ebeafb71035a484d6dc8acc1ce87246197a9d
Tx public key: 25dd9cf3f3e829fbe9c11d3dfced76143640a7ce9399c4fa04c593db61fcb5bf
Timestamp: 1576643719 Timestamp [UCT]: 2019-12-18 04:35:19 Age [y:d:h:m:s]: 05:021:18:32:17
Block: 28368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1163389 RingCT/type: yes/0
Extra: 0125dd9cf3f3e829fbe9c11d3dfced76143640a7ce9399c4fa04c593db61fcb5bf02110000002a9159db1e000000000000000000

1 output(s) for total of 494.317407557000 dcy

stealth address amount amount idx
00: 4cb58168c5a604fcf351414ae24dde9257bd918fd6405f7c7e3dc61244d93fff 494.317407557000 46912 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": 28378, "vin": [ { "gen": { "height": 28368 } } ], "vout": [ { "amount": 494317407557, "target": { "key": "4cb58168c5a604fcf351414ae24dde9257bd918fd6405f7c7e3dc61244d93fff" } } ], "extra": [ 1, 37, 221, 156, 243, 243, 232, 41, 251, 233, 193, 29, 61, 252, 237, 118, 20, 54, 64, 167, 206, 147, 153, 196, 250, 4, 197, 147, 219, 97, 252, 181, 191, 2, 17, 0, 0, 0, 42, 145, 89, 219, 30, 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