Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1215950fcf4f9ceefda8069a19c501104902208bad60aae60fcae9c27cd2d663

Tx prefix hash: 0e8651ac0854fed16b8f45a142cdaa8301a8c6405af22fb9f7eb6930e2b59234
Tx public key: 3f646c1a527d3a35b72b493f88f462f0ff8e5af8f9baf89afef27987dbfa06a8
Timestamp: 1732268649 Timestamp [UCT]: 2024-11-22 09:44:09 Age [y:d:h:m:s]: 00:001:20:48:58
Block: 1159167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1337 RingCT/type: yes/0
Extra: 013f646c1a527d3a35b72b493f88f462f0ff8e5af8f9baf89afef27987dbfa06a8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d8f6343c9cef2d162dfe2ab38ba37cd3865b4e11487ead8cf1802bc57beff0 0.600000000000 1644800 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": 1159177, "vin": [ { "gen": { "height": 1159167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d8f6343c9cef2d162dfe2ab38ba37cd3865b4e11487ead8cf1802bc57beff0" } } ], "extra": [ 1, 63, 100, 108, 26, 82, 125, 58, 53, 183, 43, 73, 63, 136, 244, 98, 240, 255, 142, 90, 248, 249, 186, 248, 154, 254, 242, 121, 135, 219, 250, 6, 168, 2, 17, 0, 0, 0, 4, 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