Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fffc22ea433ed35a6d51721107e4022fe1a14f535793893e31205460883b01f

Tx prefix hash: d4bfb9d6d267062a3ade535544b4d6b80c512fa41a5fb09c02f08231510b8422
Tx public key: f6fa4b7e438bb4347b23e6105983c2f9958fea577cceace8ceb90bda44134cd5
Timestamp: 1700144923 Timestamp [UCT]: 2023-11-16 14:28:43 Age [y:d:h:m:s]: 01:154:04:23:22
Block: 892951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371379 RingCT/type: yes/0
Extra: 01f6fa4b7e438bb4347b23e6105983c2f9958fea577cceace8ceb90bda44134cd5021100000002faf35c9c000000000000000000

1 output(s) for total of 0.674967169000 dcy

stealth address amount amount idx
00: adaa92c8a720c937708dc5c971fab21e040b13c9e4fb8d32f51f838dce7a3558 0.674967169000 1349110 of 0

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": 892961, "vin": [ { "gen": { "height": 892951 } } ], "vout": [ { "amount": 674967169, "target": { "key": "adaa92c8a720c937708dc5c971fab21e040b13c9e4fb8d32f51f838dce7a3558" } } ], "extra": [ 1, 246, 250, 75, 126, 67, 139, 180, 52, 123, 35, 230, 16, 89, 131, 194, 249, 149, 143, 234, 87, 124, 206, 172, 232, 206, 185, 11, 218, 68, 19, 76, 213, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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