Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d319cc3e13f9f79eec24fd7d1b829f504ea9b63b7fd1e88ed450ee10efaa8732

Tx prefix hash: b3c55978e2a7d4c07e15ad99620964434f75a774e727184d65a9cf0b34459f81
Tx public key: 15315d47e9b1451caa56ad0ab90173ed011756db457d05a17082ba392ce4e1e5
Timestamp: 1629180502 Timestamp [UCT]: 2021-08-17 06:08:22 Age [y:d:h:m:s]: 03:050:03:04:47
Block: 315783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 809084 RingCT/type: yes/0
Extra: 0115315d47e9b1451caa56ad0ab90173ed011756db457d05a17082ba392ce4e1e50211000000f7e6f80b5a000000000000000000

1 output(s) for total of 55.168678527000 dcy

stealth address amount amount idx
00: 8c29033e8d775eb967a53e46acb133a0eaf505d2fa44bbc27fb9c4ced55d3ad0 55.168678527000 657132 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": 315793, "vin": [ { "gen": { "height": 315783 } } ], "vout": [ { "amount": 55168678527, "target": { "key": "8c29033e8d775eb967a53e46acb133a0eaf505d2fa44bbc27fb9c4ced55d3ad0" } } ], "extra": [ 1, 21, 49, 93, 71, 233, 177, 69, 28, 170, 86, 173, 10, 185, 1, 115, 237, 1, 23, 86, 219, 69, 125, 5, 161, 112, 130, 186, 57, 44, 228, 225, 229, 2, 17, 0, 0, 0, 247, 230, 248, 11, 90, 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