Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b5596cf2a5eca3713b7f961b9253bf0aed2f4aa23161cd78172c68276c26e45

Tx prefix hash: adb5376cf6314fd31ffe143e218221be5cb8cf2ddbbaad627bdac6728b8168a0
Tx public key: 8b429bb175e5b71cb0e2caa022eba6aa75f0f3b28def1a088ca7e76188a65289
Timestamp: 1713402341 Timestamp [UCT]: 2024-04-18 01:05:41 Age [y:d:h:m:s]: 01:028:10:21:04
Block: 1002839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281295 RingCT/type: yes/0
Extra: 018b429bb175e5b71cb0e2caa022eba6aa75f0f3b28def1a088ca7e76188a65289021100000003e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c03171ce61d4c3e82adc85fc8ee653dde1650d73688a5da846faf459df19334b 0.600000000000 1463367 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": 1002849, "vin": [ { "gen": { "height": 1002839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c03171ce61d4c3e82adc85fc8ee653dde1650d73688a5da846faf459df19334b" } } ], "extra": [ 1, 139, 66, 155, 177, 117, 229, 183, 28, 176, 226, 202, 160, 34, 235, 166, 170, 117, 240, 243, 178, 141, 239, 26, 8, 140, 167, 231, 97, 136, 166, 82, 137, 2, 17, 0, 0, 0, 3, 228, 187, 107, 131, 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