Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72dfce6aec24b5ab559ce5f4e37745827a27c5bdbd88c79804e13c988ef03669

Tx prefix hash: 3508de8dc260c59bd2754bc6671c501a22c0fe5593832f35a3d2b5b61b031fd3
Tx public key: a840b089e94534e16c4de8128d12ab26637f6fbd6360965f1e986b16268b5ab8
Timestamp: 1735653133 Timestamp [UCT]: 2024-12-31 13:52:13 Age [y:d:h:m:s]: 00:303:20:22:21
Block: 1187194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214673 RingCT/type: yes/0
Extra: 01a840b089e94534e16c4de8128d12ab26637f6fbd6360965f1e986b16268b5ab8021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 923f7080e4f6b5152f38069f4c63484a3f4d0327e9aea018ad21f8e2210e4fbb 0.600000000000 1673681 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": 1187204, "vin": [ { "gen": { "height": 1187194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "923f7080e4f6b5152f38069f4c63484a3f4d0327e9aea018ad21f8e2210e4fbb" } } ], "extra": [ 1, 168, 64, 176, 137, 233, 69, 52, 225, 108, 77, 232, 18, 141, 18, 171, 38, 99, 127, 111, 189, 99, 96, 150, 95, 30, 152, 107, 22, 38, 139, 90, 184, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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