Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fd371931297915ea1deed08541ca37b9aeb1442757bcc2f95d75fba3cb9e76a

Tx prefix hash: a7fc026ed14b80e3c3a303776df31c8a987e9db471202b2adef0866d523a1699
Tx public key: 163846d543e047f900885f2b446ef38a482c1b2dce9a2caef9bd742fe9329d4b
Timestamp: 1705043316 Timestamp [UCT]: 2024-01-12 07:08:36 Age [y:d:h:m:s]: 01:096:22:44:37
Block: 933533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330409 RingCT/type: yes/0
Extra: 01163846d543e047f900885f2b446ef38a482c1b2dce9a2caef9bd742fe9329d4b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0aa94318b0805c56711f784a1754dce305d9c60628613a3cd15aba0ed0e3d46 0.600000000000 1391495 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": 933543, "vin": [ { "gen": { "height": 933533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0aa94318b0805c56711f784a1754dce305d9c60628613a3cd15aba0ed0e3d46" } } ], "extra": [ 1, 22, 56, 70, 213, 67, 224, 71, 249, 0, 136, 95, 43, 68, 110, 243, 138, 72, 44, 27, 45, 206, 154, 44, 174, 249, 189, 116, 47, 233, 50, 157, 75, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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