Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62301d1d74c28fc652982bc4839a7d86d136ab2a88a3758b742eb80ced2af4d8

Tx prefix hash: fe064b1f7ff06021405d903b9afee9457bf4741c7e9f4fce2ae5270382bd258f
Tx public key: b1fe0ee9ca927ef0ecb14096f9ebc5613f40f0bb4f173e894a534798302328f1
Timestamp: 1729002468 Timestamp [UCT]: 2024-10-15 14:27:48 Age [y:d:h:m:s]: 01:051:12:46:33
Block: 1132195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295216 RingCT/type: yes/0
Extra: 01b1fe0ee9ca927ef0ecb14096f9ebc5613f40f0bb4f173e894a534798302328f102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d27c452cbf9ea058db92c8c7898273292d720a3f2bca2c3ea600e6fbaaef2a20 0.600000000000 1615108 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": 1132205, "vin": [ { "gen": { "height": 1132195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d27c452cbf9ea058db92c8c7898273292d720a3f2bca2c3ea600e6fbaaef2a20" } } ], "extra": [ 1, 177, 254, 14, 233, 202, 146, 126, 240, 236, 177, 64, 150, 249, 235, 197, 97, 63, 64, 240, 187, 79, 23, 62, 137, 74, 83, 71, 152, 48, 35, 40, 241, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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