Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c2a60eb6f962cb2bf7ca3f1e4bbe7c9d2e4ebc98ddaa2aa7b37f5e3f94857a3

Tx prefix hash: 5e08a8339c44f77157818cab8c2b6bba2d4f2b41ed52ce2fa895eb1f4f8b4c37
Tx public key: 05f8f89e02da9b2a590cff8a81d8c85b40696c69b14db07f375065228b94237d
Timestamp: 1706859346 Timestamp [UCT]: 2024-02-02 07:35:46 Age [y:d:h:m:s]: 01:026:15:04:07
Block: 948608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280057 RingCT/type: yes/0
Extra: 0105f8f89e02da9b2a590cff8a81d8c85b40696c69b14db07f375065228b94237d02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb3cc91dceafbff95e895254d1323f59c4da7d32af23ea1851545cae065b9cc5 0.600000000000 1407052 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": 948618, "vin": [ { "gen": { "height": 948608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb3cc91dceafbff95e895254d1323f59c4da7d32af23ea1851545cae065b9cc5" } } ], "extra": [ 1, 5, 248, 248, 158, 2, 218, 155, 42, 89, 12, 255, 138, 129, 216, 200, 91, 64, 105, 108, 105, 177, 77, 176, 127, 55, 80, 101, 34, 139, 148, 35, 125, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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