Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bda2a82c7e790b0cd6f27a33d46fc346c80e1684edfe12927d95dee3e3ba0ad5

Tx prefix hash: 24440d4d981482a2b1ee88e4f3ac9a582777bb9fb7bf2bbce560b041bfaa6d48
Tx public key: ffda2830e8d84066ec4ca378e7b76e3d65dada028e671ea56eb3fc6536d7b04d
Timestamp: 1722121253 Timestamp [UCT]: 2024-07-27 23:00:53 Age [y:d:h:m:s]: 00:274:00:16:23
Block: 1075147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195757 RingCT/type: yes/0
Extra: 01ffda2830e8d84066ec4ca378e7b76e3d65dada028e671ea56eb3fc6536d7b04d02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b276a81f724a4934c0822698aacdfda14523b7b232c67b8909403c0e42558062 0.600000000000 1547670 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": 1075157, "vin": [ { "gen": { "height": 1075147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b276a81f724a4934c0822698aacdfda14523b7b232c67b8909403c0e42558062" } } ], "extra": [ 1, 255, 218, 40, 48, 232, 216, 64, 102, 236, 76, 163, 120, 231, 183, 110, 61, 101, 218, 218, 2, 142, 103, 30, 165, 110, 179, 252, 101, 54, 215, 176, 77, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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