Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb37c836848369cba075442c20bc657fd4bcf8797a207505f06a95c0d5bc74a2

Tx prefix hash: da59ffbad55e02b324ce68b37c0b86cf242d2ceea51951618b4efd5c2c957fc5
Tx public key: a5c19c4524039a153db1bcc6143e2c3335c6700e51b2244670e1cf60bf1952d8
Timestamp: 1629293033 Timestamp [UCT]: 2021-08-18 13:23:53 Age [y:d:h:m:s]: 03:090:00:34:20
Block: 316445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 837838 RingCT/type: yes/0
Extra: 01a5c19c4524039a153db1bcc6143e2c3335c6700e51b2244670e1cf60bf1952d802110000000be6f80b5a000000000000000000

1 output(s) for total of 54.889189607000 dcy

stealth address amount amount idx
00: 45e44bb12cd18fa9e40247a577db8c3dc9aa1fa15a885e2d005f8a8daa6f539f 54.889189607000 658338 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": 316455, "vin": [ { "gen": { "height": 316445 } } ], "vout": [ { "amount": 54889189607, "target": { "key": "45e44bb12cd18fa9e40247a577db8c3dc9aa1fa15a885e2d005f8a8daa6f539f" } } ], "extra": [ 1, 165, 193, 156, 69, 36, 3, 154, 21, 61, 177, 188, 198, 20, 62, 44, 51, 53, 198, 112, 14, 81, 178, 36, 70, 112, 225, 207, 96, 191, 25, 82, 216, 2, 17, 0, 0, 0, 11, 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