Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b76954a094e83038cc12123fd8584b6755c8df6d0638c8723384aba841a86c8a

Tx prefix hash: 052f02344da5643e53a4a0c3846926c67d8acc05084f1a33d854ddb458bf3fed
Tx public key: c4d6a7d3b3ec1dfbe35425be8f5ec60db9594193124074976b5ef3226aa108e6
Timestamp: 1722935518 Timestamp [UCT]: 2024-08-06 09:11:58 Age [y:d:h:m:s]: 00:263:14:31:23
Block: 1081883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188315 RingCT/type: yes/0
Extra: 01c4d6a7d3b3ec1dfbe35425be8f5ec60db9594193124074976b5ef3226aa108e6021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0777f5a043a0884ce770454dfc7f3c8db38f13e2ab94b4f7fe3bd683d4258e70 0.600000000000 1555706 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": 1081893, "vin": [ { "gen": { "height": 1081883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0777f5a043a0884ce770454dfc7f3c8db38f13e2ab94b4f7fe3bd683d4258e70" } } ], "extra": [ 1, 196, 214, 167, 211, 179, 236, 29, 251, 227, 84, 37, 190, 143, 94, 198, 13, 185, 89, 65, 147, 18, 64, 116, 151, 107, 94, 243, 34, 106, 161, 8, 230, 2, 17, 0, 0, 0, 1, 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