Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 901fdf51d67c91b596c49dbba724a61b2df9df527b3b56828ac5a1d6395d651f

Tx prefix hash: 824368ea9c036c36e3fbb209c4c6f2c7ad891148d7f4ec7d6c8dcef2237754a7
Tx public key: 31949be70cfb472404298f378b26f69f7ca7a064925996fd45228797399c0660
Timestamp: 1705701723 Timestamp [UCT]: 2024-01-19 22:02:03 Age [y:d:h:m:s]: 01:292:13:43:59
Block: 938985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467932 RingCT/type: yes/0
Extra: 0131949be70cfb472404298f378b26f69f7ca7a064925996fd45228797399c066002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64de4c81b220d1855496823aeb3e2bdd8c8be9e3684da5b4be609d5204ef287f 0.600000000000 1397069 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": 938995, "vin": [ { "gen": { "height": 938985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64de4c81b220d1855496823aeb3e2bdd8c8be9e3684da5b4be609d5204ef287f" } } ], "extra": [ 1, 49, 148, 155, 231, 12, 251, 71, 36, 4, 41, 143, 55, 139, 38, 246, 159, 124, 167, 160, 100, 146, 89, 150, 253, 69, 34, 135, 151, 57, 156, 6, 96, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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