Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dc073f507dd2582be51fb6849d128e1c701a20cfdf255b9c5d458a9337f973a

Tx prefix hash: 7fa6e96ea58ce00fee444db5c45a48420139774305d2a45bbaeec5ea19700cc1
Tx public key: 855e4232048b621f675ecb237da6744677176d1f9b5f44a5f45df61fd1413614
Timestamp: 1577755364 Timestamp [UCT]: 2019-12-31 01:22:44 Age [y:d:h:m:s]: 05:055:21:40:33
Block: 35407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1189687 RingCT/type: yes/0
Extra: 01855e4232048b621f675ecb237da6744677176d1f9b5f44a5f45df61fd141361402110000001b8a2ee0d9000000000000000000

1 output(s) for total of 468.471057727000 dcy

stealth address amount amount idx
00: b3160b9790326aef8c9497c24623a3d64d3d72339d29c30e7c3cfd90d6a25397 468.471057727000 59699 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": 35417, "vin": [ { "gen": { "height": 35407 } } ], "vout": [ { "amount": 468471057727, "target": { "key": "b3160b9790326aef8c9497c24623a3d64d3d72339d29c30e7c3cfd90d6a25397" } } ], "extra": [ 1, 133, 94, 66, 50, 4, 139, 98, 31, 103, 94, 203, 35, 125, 166, 116, 70, 119, 23, 109, 31, 155, 95, 68, 165, 244, 93, 246, 31, 209, 65, 54, 20, 2, 17, 0, 0, 0, 27, 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