Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31a4bf3e505f9e1b78788fac226a328d1d431e555951f102f6aa34acba5d1b70

Tx prefix hash: ab0637b8a9bc25d1011e0bbca853a5517d229af3085f097197d559f199d228f2
Tx public key: b29071777f9f15dd0f383701b36c5a98644fdb6add56c921b8cf8061c5a50a66
Timestamp: 1700811974 Timestamp [UCT]: 2023-11-24 07:46:14 Age [y:d:h:m:s]: 01:058:09:13:45
Block: 898478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303065 RingCT/type: yes/0
Extra: 01b29071777f9f15dd0f383701b36c5a98644fdb6add56c921b8cf8061c5a50a6602110000000633af99f4000000000000000000

1 output(s) for total of 0.647097014000 dcy

stealth address amount amount idx
00: 9cc9719e867b7dc5ec9b51e02514b90d0e2afb20de4390126563242915fc84e1 0.647097014000 1354897 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": 898488, "vin": [ { "gen": { "height": 898478 } } ], "vout": [ { "amount": 647097014, "target": { "key": "9cc9719e867b7dc5ec9b51e02514b90d0e2afb20de4390126563242915fc84e1" } } ], "extra": [ 1, 178, 144, 113, 119, 127, 159, 21, 221, 15, 56, 55, 1, 179, 108, 90, 152, 100, 79, 219, 106, 221, 86, 201, 33, 184, 207, 128, 97, 197, 165, 10, 102, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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