Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc02f1c94d62ec36420d6882a997b8322efa94d9b5869e74ec16a06864bd82c6

Tx prefix hash: 536a8cbdd608756044cbc6cfb0ca98b6b90ac3fc4ec44a327c0f552acc66359e
Tx public key: 0c8d3063ea88f1e2564108d1c42de41e385897322a9922ca4f5e4fce5f28f60a
Timestamp: 1714320712 Timestamp [UCT]: 2024-04-28 16:11:52 Age [y:d:h:m:s]: 01:218:02:35:57
Block: 1010461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414566 RingCT/type: yes/0
Extra: 010c8d3063ea88f1e2564108d1c42de41e385897322a9922ca4f5e4fce5f28f60a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a11dff3984c351da9646c9b16c6bb31e5a75b91a72ed6ff42c2077e3b1467dd 0.600000000000 1472427 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": 1010471, "vin": [ { "gen": { "height": 1010461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a11dff3984c351da9646c9b16c6bb31e5a75b91a72ed6ff42c2077e3b1467dd" } } ], "extra": [ 1, 12, 141, 48, 99, 234, 136, 241, 226, 86, 65, 8, 209, 196, 45, 228, 30, 56, 88, 151, 50, 42, 153, 34, 202, 79, 94, 79, 206, 95, 40, 246, 10, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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