Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8f1225c1d208271003aeb0bd98b221bc51b91b2337d696b7864dc2aeebc76b4

Tx prefix hash: 86bb201c5e9d2073f872159e8f29b1876e641eff5d106fd526ae3f7b957aa556
Tx public key: 54d96ca7920eb0483d44d0b313d0e4dbf3b1079e441afa49b371cda6f0b47dfc
Timestamp: 1716602965 Timestamp [UCT]: 2024-05-25 02:09:25 Age [y:d:h:m:s]: 00:320:08:40:09
Block: 1029400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228968 RingCT/type: yes/0
Extra: 0154d96ca7920eb0483d44d0b313d0e4dbf3b1079e441afa49b371cda6f0b47dfc02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cbfff4945992de0c2e77dfa6d650f536cf59d81e0e8bfb277af61ea1588a456 0.600000000000 1497479 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": 1029410, "vin": [ { "gen": { "height": 1029400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cbfff4945992de0c2e77dfa6d650f536cf59d81e0e8bfb277af61ea1588a456" } } ], "extra": [ 1, 84, 217, 108, 167, 146, 14, 176, 72, 61, 68, 208, 179, 19, 208, 228, 219, 243, 177, 7, 158, 68, 26, 250, 73, 179, 113, 205, 166, 240, 180, 125, 252, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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