Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c0efb8821d9f8377be399e6ffdd667628788deb22d88b5906a952e5715efdf5

Tx prefix hash: 72af0009286fbdc6f89ec37865e4c3d8d639249c14bb23c44693b32bb9cea3c7
Tx public key: 8622d356d16427493675b4ecf271e0ed04f4d2a25b553beca8a271656f37fd9f
Timestamp: 1711683271 Timestamp [UCT]: 2024-03-29 03:34:31 Age [y:d:h:m:s]: 01:061:12:07:16
Block: 988622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304951 RingCT/type: yes/0
Extra: 018622d356d16427493675b4ecf271e0ed04f4d2a25b553beca8a271656f37fd9f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06364b339d81dc0a10f579200612f2f41652278d050e99b3c046f5ab028b0fd4 0.600000000000 1448903 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": 988632, "vin": [ { "gen": { "height": 988622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06364b339d81dc0a10f579200612f2f41652278d050e99b3c046f5ab028b0fd4" } } ], "extra": [ 1, 134, 34, 211, 86, 209, 100, 39, 73, 54, 117, 180, 236, 242, 113, 224, 237, 4, 244, 210, 162, 91, 85, 59, 236, 168, 162, 113, 101, 111, 55, 253, 159, 2, 17, 0, 0, 0, 2, 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