Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcabd2891f1888c6279f81f59de173488a90bb1ea1bdd012434a7e9d1071545c

Tx prefix hash: 39d4b6f9bca824cdcf76324105ad8a8f0b5750e5f894387d7c01ef47d68c4c93
Tx public key: 38cd553cedc92e76d1006e253fc7d07268f5ec802f40cb945667d1279956a671
Timestamp: 1725592719 Timestamp [UCT]: 2024-09-06 03:18:39 Age [y:d:h:m:s]: 00:126:16:52:38
Block: 1103919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90621 RingCT/type: yes/0
Extra: 0138cd553cedc92e76d1006e253fc7d07268f5ec802f40cb945667d1279956a671021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8449c5b961f5c0c644dc20dc6b4443df173b66f88f22de8a2dd9047f8b13faab 0.600000000000 1580934 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": 1103929, "vin": [ { "gen": { "height": 1103919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8449c5b961f5c0c644dc20dc6b4443df173b66f88f22de8a2dd9047f8b13faab" } } ], "extra": [ 1, 56, 205, 85, 60, 237, 201, 46, 118, 209, 0, 110, 37, 63, 199, 208, 114, 104, 245, 236, 128, 47, 64, 203, 148, 86, 103, 209, 39, 153, 86, 166, 113, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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