Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c310b1a113b3b0f3dc67e4a000099d3b02dfde44d835e9bff8fc79cf68e6ad4

Tx prefix hash: 921bb33fefbf763824f43ac2e4440046aa7bab39620339071270aeeacbc38c88
Tx public key: 6cd6b4f8e18b7e07e5bab6bcd94dd1adb87d01e4037cf72b919f4ee724eca1bc
Timestamp: 1713770966 Timestamp [UCT]: 2024-04-22 07:29:26 Age [y:d:h:m:s]: 00:349:02:03:37
Block: 1005911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249554 RingCT/type: yes/0
Extra: 016cd6b4f8e18b7e07e5bab6bcd94dd1adb87d01e4037cf72b919f4ee724eca1bc02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b27adcfdcaa8ade4e75b57aaaec611c414317e77ec96d8ec32e3be171f0836e 0.600000000000 1466761 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": 1005921, "vin": [ { "gen": { "height": 1005911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b27adcfdcaa8ade4e75b57aaaec611c414317e77ec96d8ec32e3be171f0836e" } } ], "extra": [ 1, 108, 214, 180, 248, 225, 139, 126, 7, 229, 186, 182, 188, 217, 77, 209, 173, 184, 125, 1, 228, 3, 124, 247, 43, 145, 159, 78, 231, 36, 236, 161, 188, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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