Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb567d44744fe05b88d3403ea85c79012bbe0190bab5038c07dc8db4eecd9a4

Tx prefix hash: b9db4fa341ba3c42007979216832c78de8f2c90d56700762cfab0b70d7c0c959
Tx public key: a4bea6622c629bd7f9b9df6630f0a51b304bc6865fc7a1762064f41c33bfd108
Timestamp: 1738432078 Timestamp [UCT]: 2025-02-01 17:47:58 Age [y:d:h:m:s]: 00:292:10:40:06
Block: 1209940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206760 RingCT/type: yes/0
Extra: 01a4bea6622c629bd7f9b9df6630f0a51b304bc6865fc7a1762064f41c33bfd1080211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37b5479c1a72eb1d931e5e2c93723f8485da99343e49c9aa44eae05fcf54f5fc 0.600000000000 1696687 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": 1209950, "vin": [ { "gen": { "height": 1209940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37b5479c1a72eb1d931e5e2c93723f8485da99343e49c9aa44eae05fcf54f5fc" } } ], "extra": [ 1, 164, 190, 166, 98, 44, 98, 155, 215, 249, 185, 223, 102, 48, 240, 165, 27, 48, 75, 198, 134, 95, 199, 161, 118, 32, 100, 244, 28, 51, 191, 209, 8, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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