Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a95de4b2928c3526ce7cebd32eb3623fbcdf97031391d05e7dd130e4b89f650

Tx prefix hash: 855a386e003433d7dd8bd5d73e6ba7356436b6911b84a882a4f1e6243b03764d
Tx public key: 2b7dd6c42d077dfc569796851f1d57ec8ae60a65b35b1a80bcddc83298aea7b5
Timestamp: 1712360052 Timestamp [UCT]: 2024-04-05 23:34:12 Age [y:d:h:m:s]: 00:357:22:43:48
Block: 994181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255949 RingCT/type: yes/0
Extra: 012b7dd6c42d077dfc569796851f1d57ec8ae60a65b35b1a80bcddc83298aea7b50211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a7d2cfb9ef93cffee67cf737a7effffb17b1c3a45916c17c0c873581598d15d 0.600000000000 1454583 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": 994191, "vin": [ { "gen": { "height": 994181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a7d2cfb9ef93cffee67cf737a7effffb17b1c3a45916c17c0c873581598d15d" } } ], "extra": [ 1, 43, 125, 214, 196, 45, 7, 125, 252, 86, 151, 150, 133, 31, 29, 87, 236, 138, 230, 10, 101, 179, 91, 26, 128, 188, 221, 200, 50, 152, 174, 167, 181, 2, 17, 0, 0, 0, 3, 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