Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b84e6d9149658cd816e643e263db7299eb7a1e6f3c77294a764c97a38df542ac

Tx prefix hash: 966101cdfa86038d54d7fda9a271a49bbb972ffb18e5abe8632d86f19bc59ce3
Tx public key: 383932f5c2858bb93829ae2889c69b4edce6844c58802280e386e5f2d9a6544b
Timestamp: 1726904456 Timestamp [UCT]: 2024-09-21 07:40:56 Age [y:d:h:m:s]: 01:046:18:02:33
Block: 1114795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291807 RingCT/type: yes/0
Extra: 01383932f5c2858bb93829ae2889c69b4edce6844c58802280e386e5f2d9a6544b02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a6edb20d08945d1c7d5417022312ae13bdefc583fb09963b47522938002ea3a 0.600000000000 1594700 of 15

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": 1114805, "vin": [ { "gen": { "height": 1114795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a6edb20d08945d1c7d5417022312ae13bdefc583fb09963b47522938002ea3a" } } ], "extra": [ 1, 56, 57, 50, 245, 194, 133, 139, 185, 56, 41, 174, 40, 137, 198, 155, 78, 220, 230, 132, 76, 88, 128, 34, 128, 227, 134, 229, 242, 217, 166, 84, 75, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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