Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55773caac77d0f1c4a2ec6be1ad6164aec450b6b80bd523c338e761afa072b07

Tx prefix hash: 515caa54970bfe1e4009ac3e91e0f58643b30f7370708f74b0ba0b07f5803b8d
Tx public key: 07b851d19ac68a1d916c639883be8911fdaebdd0bd875b1086693dc95465943b
Timestamp: 1727330986 Timestamp [UCT]: 2024-09-26 06:09:46 Age [y:d:h:m:s]: 01:055:16:23:31
Block: 1118332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298202 RingCT/type: yes/0
Extra: 0107b851d19ac68a1d916c639883be8911fdaebdd0bd875b1086693dc95465943b02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abc44bf7d0d478f8df532e3dbf2491fd9a5f01c38e979eb7c1c543f1f49dbeac 0.600000000000 1599487 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": 1118342, "vin": [ { "gen": { "height": 1118332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abc44bf7d0d478f8df532e3dbf2491fd9a5f01c38e979eb7c1c543f1f49dbeac" } } ], "extra": [ 1, 7, 184, 81, 209, 154, 198, 138, 29, 145, 108, 99, 152, 131, 190, 137, 17, 253, 174, 189, 208, 189, 135, 91, 16, 134, 105, 61, 201, 84, 101, 148, 59, 2, 17, 0, 0, 0, 7, 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