Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92c5c228d6c4d36cd64f4d91c941591a690d0b6339e1c78898527d3de9353774

Tx prefix hash: 71823446f76bac5d5ad8bebd01cac354de18b26eac24e297cc5e4d03aa48da1c
Tx public key: 5df844a166ce8a6849833b2ae368e40fa4dfa20a2e0bf9385c70e7d7360fa1b4
Timestamp: 1703211713 Timestamp [UCT]: 2023-12-22 02:21:53 Age [y:d:h:m:s]: 01:097:21:37:52
Block: 918366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331092 RingCT/type: yes/0
Extra: 015df844a166ce8a6849833b2ae368e40fa4dfa20a2e0bf9385c70e7d7360fa1b402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bc087e669939f8815b5f6e47a4dc476d31d8910caa8745705d79bb5c21f7181 0.600000000000 1376010 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": 918376, "vin": [ { "gen": { "height": 918366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bc087e669939f8815b5f6e47a4dc476d31d8910caa8745705d79bb5c21f7181" } } ], "extra": [ 1, 93, 248, 68, 161, 102, 206, 138, 104, 73, 131, 59, 42, 227, 104, 228, 15, 164, 223, 162, 10, 46, 11, 249, 56, 92, 112, 231, 215, 54, 15, 161, 180, 2, 17, 0, 0, 0, 2, 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