Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f64c1025ccbed6a71c8b2177ce6dcbc2f04392064f1b4d87dba9bd96accbf13

Tx prefix hash: ca65079c51f582da0048f8dc8061a980adf4ab0953e6fa1394a7d4d002b97549
Tx public key: d2cba6450e6d3759b0f5549763439b1c72ac366cefa181a1672f11c12da5a113
Timestamp: 1727485200 Timestamp [UCT]: 2024-09-28 01:00:00 Age [y:d:h:m:s]: 00:258:10:28:04
Block: 1119614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184498 RingCT/type: yes/0
Extra: 01d2cba6450e6d3759b0f5549763439b1c72ac366cefa181a1672f11c12da5a113021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d99c7a7df9d4e25a15a86d5f3f2fbd48902c783fc3c7c210caf090bad1de3e2 0.600000000000 1601237 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": 1119624, "vin": [ { "gen": { "height": 1119614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d99c7a7df9d4e25a15a86d5f3f2fbd48902c783fc3c7c210caf090bad1de3e2" } } ], "extra": [ 1, 210, 203, 166, 69, 14, 109, 55, 89, 176, 245, 84, 151, 99, 67, 155, 28, 114, 172, 54, 108, 239, 161, 129, 161, 103, 47, 17, 193, 45, 165, 161, 19, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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