Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93effb56c269318aff5c1aa981e8f27988253d20435a817d528aa7d10ef747a8

Tx prefix hash: ec7485b456f5167b7004031fc1e8785b48bdd6e1be57aace4a144df4f4aa9c2e
Tx public key: 959a519e959dcc59219bbed8a0cefa2ad16da75a32a37338ecc47c28da316d5e
Timestamp: 1709559309 Timestamp [UCT]: 2024-03-04 13:35:09 Age [y:d:h:m:s]: 00:326:07:43:27
Block: 971003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233532 RingCT/type: yes/0
Extra: 01959a519e959dcc59219bbed8a0cefa2ad16da75a32a37338ecc47c28da316d5e0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b50f3226dfa0d02556ee1b6abaa862833f676f7fee7040f1862c6f220f4c0e4f 0.600000000000 1430876 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": 971013, "vin": [ { "gen": { "height": 971003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b50f3226dfa0d02556ee1b6abaa862833f676f7fee7040f1862c6f220f4c0e4f" } } ], "extra": [ 1, 149, 154, 81, 158, 149, 157, 204, 89, 33, 155, 190, 216, 160, 206, 250, 42, 209, 109, 167, 90, 50, 163, 115, 56, 236, 196, 124, 40, 218, 49, 109, 94, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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