Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a1d757ead8d854a4b61b99bd1dab3f97149a7fc1ddf2dea5de6b615a775a810

Tx prefix hash: e65288985e66543cfb33581de48a3a5c71366c36095be71401f93e9ac3fd931d
Tx public key: cc6250e171224932acae852d6c4da44a1ed12c8828702ccc9dd3b9e7428734fd
Timestamp: 1717870977 Timestamp [UCT]: 2024-06-08 18:22:57 Age [y:d:h:m:s]: 00:281:03:08:44
Block: 1039910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200914 RingCT/type: yes/0
Extra: 01cc6250e171224932acae852d6c4da44a1ed12c8828702ccc9dd3b9e7428734fd0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15959277d6db00c841f09e5153d98ce7ce0ae25c7c23d46d1a3b4f98f0d5cddb 0.600000000000 1508565 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": 1039920, "vin": [ { "gen": { "height": 1039910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15959277d6db00c841f09e5153d98ce7ce0ae25c7c23d46d1a3b4f98f0d5cddb" } } ], "extra": [ 1, 204, 98, 80, 225, 113, 34, 73, 50, 172, 174, 133, 45, 108, 77, 164, 74, 30, 209, 44, 136, 40, 112, 44, 204, 157, 211, 185, 231, 66, 135, 52, 253, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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