Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c64eda81f9f5e21e875f009c8953ac24ec537930efd26206c2073bafdbbd8bf2

Tx prefix hash: 4bd1242555b4f5ab67f22887e3ce03e6543271dff8f82ca2c2c9180eabd8a258
Tx public key: 0b4ae820dbce1ef81cb697dddfe790b5f43c71c11781ef09a0cf1ab13cb73713
Timestamp: 1716182646 Timestamp [UCT]: 2024-05-20 05:24:06 Age [y:d:h:m:s]: 00:248:03:57:45
Block: 1025911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177558 RingCT/type: yes/0
Extra: 010b4ae820dbce1ef81cb697dddfe790b5f43c71c11781ef09a0cf1ab13cb7371302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26f77c05b883d3d6e3a05fdab9857a021d64ad2cf90480e6c0ae9302cde4ef6d 0.600000000000 1492702 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": 1025921, "vin": [ { "gen": { "height": 1025911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26f77c05b883d3d6e3a05fdab9857a021d64ad2cf90480e6c0ae9302cde4ef6d" } } ], "extra": [ 1, 11, 74, 232, 32, 219, 206, 30, 248, 28, 182, 151, 221, 223, 231, 144, 181, 244, 60, 113, 193, 23, 129, 239, 9, 160, 207, 26, 177, 60, 183, 55, 19, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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