Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf6595631975f585d063f53260ceecc12d8f0e4cbd305006ccd9ab2581add5c5

Tx prefix hash: 27187d1a4f6bf08577faf6b11d1af6b298be94c85f02a69f0ef45b52c49a4b81
Tx public key: a112b8d7d3e6b0dbc61ac5cc5e71d145d6c71cf4a654178d67f690bb9aee8bd7
Timestamp: 1698610569 Timestamp [UCT]: 2023-10-29 20:16:09 Age [y:d:h:m:s]: 01:162:11:02:28
Block: 880439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377107 RingCT/type: yes/0
Extra: 01a112b8d7d3e6b0dbc61ac5cc5e71d145d6c71cf4a654178d67f690bb9aee8bd7021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.742574647000 dcy

stealth address amount amount idx
00: a71e11220715f3a24f458b7c07ce47e6afa9137687b3d44b3f06eae2cd882b28 0.742574647000 1335997 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": 880449, "vin": [ { "gen": { "height": 880439 } } ], "vout": [ { "amount": 742574647, "target": { "key": "a71e11220715f3a24f458b7c07ce47e6afa9137687b3d44b3f06eae2cd882b28" } } ], "extra": [ 1, 161, 18, 184, 215, 211, 230, 176, 219, 198, 26, 197, 204, 94, 113, 209, 69, 214, 199, 28, 244, 166, 84, 23, 141, 103, 246, 144, 187, 154, 238, 139, 215, 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