Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1125bd40b9be9743d43a9a44b904ceeb158d6a165482c9a2f160fe84d1dafacb

Tx prefix hash: 50efbf8508e4b23ee5b226c1da3a743b3017073046bfa949543a9b9b5cd56ed1
Tx public key: f625a6b1f7f254ddd8f8732b731997c7cb769891704f888c6ba5fd8fc23da24a
Timestamp: 1713517343 Timestamp [UCT]: 2024-04-19 09:02:23 Age [y:d:h:m:s]: 01:196:05:16:55
Block: 1003810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398906 RingCT/type: yes/0
Extra: 01f625a6b1f7f254ddd8f8732b731997c7cb769891704f888c6ba5fd8fc23da24a02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55dd61f094900c3f3dd99349662aebce824768e898d803249ddd72f1b47566c3 0.600000000000 1464356 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": 1003820, "vin": [ { "gen": { "height": 1003810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55dd61f094900c3f3dd99349662aebce824768e898d803249ddd72f1b47566c3" } } ], "extra": [ 1, 246, 37, 166, 177, 247, 242, 84, 221, 216, 248, 115, 43, 115, 25, 151, 199, 203, 118, 152, 145, 112, 79, 136, 140, 107, 165, 253, 143, 194, 61, 162, 74, 2, 17, 0, 0, 0, 6, 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