Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c747a551a72e976bd0987ba92dd4bf510ac270b2035c4c989b421dc3d15a7d7

Tx prefix hash: f5304e64a862f8824ceae9461c63867c049871bd1b85e7405f73e191fde07b25
Tx public key: 7ab8c9a4f4716f9ecd99bb8b015d5f8dedf48091d54ca69ee0c920ec169b7338
Timestamp: 1745801090 Timestamp [UCT]: 2025-04-28 00:44:50 Age [y:d:h:m:s]: 00:013:16:29:36
Block: 1270947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9783 RingCT/type: yes/0
Extra: 017ab8c9a4f4716f9ecd99bb8b015d5f8dedf48091d54ca69ee0c920ec169b73380211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a546b164ea3ea814fd9493b021fbbfa28363083e2cce08f591025a65a5d562af 0.600000000000 1758192 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": 1270957, "vin": [ { "gen": { "height": 1270947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a546b164ea3ea814fd9493b021fbbfa28363083e2cce08f591025a65a5d562af" } } ], "extra": [ 1, 122, 184, 201, 164, 244, 113, 111, 158, 205, 153, 187, 139, 1, 93, 95, 141, 237, 244, 128, 145, 213, 76, 166, 158, 224, 201, 32, 236, 22, 155, 115, 56, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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