Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7532670ccbeda240cc437a779029cfa28113e47f9aac55d05e71a53dff493d8

Tx prefix hash: ad4054afee8d36f32f946ac92173c9de68c6b475b2982966f50febd8f9bebea5
Tx public key: 76811b1b567ea2e4852e6e2eaa26d2d1ae7812f0ca668f76f5d0eaee223a92c1
Timestamp: 1736915596 Timestamp [UCT]: 2025-01-15 04:33:16 Age [y:d:h:m:s]: 00:153:13:45:42
Block: 1197639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109474 RingCT/type: yes/0
Extra: 0176811b1b567ea2e4852e6e2eaa26d2d1ae7812f0ca668f76f5d0eaee223a92c1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2701ba348bc0f95874798f61e66ee88977432a3a5085d8c5658be671ee20cd9d 0.600000000000 1684252 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": 1197649, "vin": [ { "gen": { "height": 1197639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2701ba348bc0f95874798f61e66ee88977432a3a5085d8c5658be671ee20cd9d" } } ], "extra": [ 1, 118, 129, 27, 27, 86, 126, 162, 228, 133, 46, 110, 46, 170, 38, 210, 209, 174, 120, 18, 240, 202, 102, 143, 118, 245, 208, 234, 238, 34, 58, 146, 193, 2, 17, 0, 0, 0, 2, 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