Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd0527b4cb77b9be8c6e8e8787d7e09b7be9391542d95dccada46ae26a4f2252

Tx prefix hash: 08ec242d9380fa8a88e901110e63d6fe7fa89d2f141931606b20fc90d957fe14
Tx public key: 983d2ef442fa6bc1f21fbd0c7d880e0867000d86a92e4249ef4bc3f7681fa3ee
Timestamp: 1713160433 Timestamp [UCT]: 2024-04-15 05:53:53 Age [y:d:h:m:s]: 01:199:00:59:01
Block: 1000843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400919 RingCT/type: yes/0
Extra: 01983d2ef442fa6bc1f21fbd0c7d880e0867000d86a92e4249ef4bc3f7681fa3ee02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 585dbf8cb4f642054974adb222666a9dbf3c2c9a3bbcc9d2a7a74698a27ad021 0.600000000000 1461343 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": 1000853, "vin": [ { "gen": { "height": 1000843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "585dbf8cb4f642054974adb222666a9dbf3c2c9a3bbcc9d2a7a74698a27ad021" } } ], "extra": [ 1, 152, 61, 46, 244, 66, 250, 107, 193, 242, 31, 189, 12, 125, 136, 14, 8, 103, 0, 13, 134, 169, 46, 66, 73, 239, 75, 195, 247, 104, 31, 163, 238, 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