Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2234942e1d218476bf6e928bf8593f126db6bc9c7b2d4283361646fe3bd5df53

Tx prefix hash: af2a0a0f9fb47ba1427ed65515a3711e2285919256031119338eef58ee81fb74
Tx public key: 811f2b8c2df8a0bcf0716e9d3a4d8bae9727cc0a8c240b631862b4caa77d0fc0
Timestamp: 1730660703 Timestamp [UCT]: 2024-11-03 19:05:03 Age [y:d:h:m:s]: 00:147:16:56:58
Block: 1145856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105396 RingCT/type: yes/0
Extra: 01811f2b8c2df8a0bcf0716e9d3a4d8bae9727cc0a8c240b631862b4caa77d0fc0021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3d23d8a431d84bbddef4107a2bbec3a5a86cc53a74bd170c78c2ea14224bf1c 0.600000000000 1630381 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": 1145866, "vin": [ { "gen": { "height": 1145856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3d23d8a431d84bbddef4107a2bbec3a5a86cc53a74bd170c78c2ea14224bf1c" } } ], "extra": [ 1, 129, 31, 43, 140, 45, 248, 160, 188, 240, 113, 110, 157, 58, 77, 139, 174, 151, 39, 204, 10, 140, 36, 11, 99, 24, 98, 180, 202, 167, 125, 15, 192, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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