Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2e68deef954c58b76f3690d918173c5985cf06cd71952a41960d8f85dc9c8b2

Tx prefix hash: cdf01af960c4ff89b438abc6723af6ad252de206d574ffe4934f4cdb9da1acc6
Tx public key: 2143b81b91602751f6bde5cf06683b7f2538e9c939961031bd42eaa0e4742123
Timestamp: 1698344189 Timestamp [UCT]: 2023-10-26 18:16:29 Age [y:d:h:m:s]: 01:196:15:19:27
Block: 878240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401545 RingCT/type: yes/0
Extra: 012143b81b91602751f6bde5cf06683b7f2538e9c939961031bd42eaa0e4742123021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.755137992000 dcy

stealth address amount amount idx
00: 3e0a4a4a3c0a37cff0e9a005d71feef8fd7b2d66004275269d2393fcea721722 0.755137992000 1333666 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": 878250, "vin": [ { "gen": { "height": 878240 } } ], "vout": [ { "amount": 755137992, "target": { "key": "3e0a4a4a3c0a37cff0e9a005d71feef8fd7b2d66004275269d2393fcea721722" } } ], "extra": [ 1, 33, 67, 184, 27, 145, 96, 39, 81, 246, 189, 229, 207, 6, 104, 59, 127, 37, 56, 233, 201, 57, 150, 16, 49, 189, 66, 234, 160, 228, 116, 33, 35, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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