Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca4ba30e23f8a95b299dc63f35c6530dc9f522ca55e8ce7f2982b34f07ac877b

Tx prefix hash: 7ef0c07bf72968f6927915798dd73648c36d0ead6d1517ad035ca1759b1b9398
Tx public key: 4657276b36e2f5f883fd8c58ff55bba96c7b307892930876d5024caf2422b973
Timestamp: 1708815128 Timestamp [UCT]: 2024-02-24 22:52:08 Age [y:d:h:m:s]: 01:044:09:00:13
Block: 964833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292727 RingCT/type: yes/0
Extra: 014657276b36e2f5f883fd8c58ff55bba96c7b307892930876d5024caf2422b97302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb8dc94e42c637e71dcb58bb85ea39c43605c1798e7b7e09f1bd164efb932ae 0.600000000000 1424576 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": 964843, "vin": [ { "gen": { "height": 964833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb8dc94e42c637e71dcb58bb85ea39c43605c1798e7b7e09f1bd164efb932ae" } } ], "extra": [ 1, 70, 87, 39, 107, 54, 226, 245, 248, 131, 253, 140, 88, 255, 85, 187, 169, 108, 123, 48, 120, 146, 147, 8, 118, 213, 2, 76, 175, 36, 34, 185, 115, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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