Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57bcf85a70fa5786c1593d4f4ab6e52b02f1d6564369c928bef4ea62cef95001

Tx prefix hash: fbe64077a63e0d05c260f673f8b1b6ceb22525c9b5d67c5b8cc343382343fe7a
Tx public key: be8b592fc38f5948d499c609ef83cb846e11c98bfcaf021155c24c88e205be15
Timestamp: 1745116702 Timestamp [UCT]: 2025-04-20 02:38:22 Age [y:d:h:m:s]: 00:215:23:25:05
Block: 1265281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152069 RingCT/type: yes/0
Extra: 01be8b592fc38f5948d499c609ef83cb846e11c98bfcaf021155c24c88e205be15021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 825b950edb9a928c6b40a88e85468186ae84378a0a4c96a0ea8cb6aac12421b5 0.600000000000 1752486 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": 1265291, "vin": [ { "gen": { "height": 1265281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "825b950edb9a928c6b40a88e85468186ae84378a0a4c96a0ea8cb6aac12421b5" } } ], "extra": [ 1, 190, 139, 89, 47, 195, 143, 89, 72, 212, 153, 198, 9, 239, 131, 203, 132, 110, 17, 201, 139, 252, 175, 2, 17, 85, 194, 76, 136, 226, 5, 190, 21, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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