Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdef017ee7c1cba7f13734f9c092cfabb782b7f9d857abf859bf2aaafc617d02

Tx prefix hash: 4a8299d92c202dbaf3073a847fb112ac37e1b4fdbe204e5e17e1e6f3aa6e718a
Tx public key: c5d9e92d7139aeb5104abc119f8cc8fb95e645e33d7e9edc1aeba7e8b52065fd
Timestamp: 1738976347 Timestamp [UCT]: 2025-02-08 00:59:07 Age [y:d:h:m:s]: 00:356:05:18:55
Block: 1214449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252270 RingCT/type: yes/0
Extra: 01c5d9e92d7139aeb5104abc119f8cc8fb95e645e33d7e9edc1aeba7e8b52065fd021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8839c423866c27d7ca20ce3cc99c903bd29983261207039d2a3b815c7f8c35ea 0.600000000000 1701240 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": 1214459, "vin": [ { "gen": { "height": 1214449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8839c423866c27d7ca20ce3cc99c903bd29983261207039d2a3b815c7f8c35ea" } } ], "extra": [ 1, 197, 217, 233, 45, 113, 57, 174, 181, 16, 74, 188, 17, 159, 140, 200, 251, 149, 230, 69, 227, 61, 126, 158, 220, 26, 235, 167, 232, 181, 32, 101, 253, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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