Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56496ae6d35db04ffebb275276a07a61b61f2488c0a6648cdbfde1f6538e17ec

Tx prefix hash: b8af6f52d89533e3c19c741a2dbd651bd4e30d0f2daafb03d395f9452371dd59
Tx public key: acb680c18f98243c5f7459592a99f2a681e3281774ace881a9d07b3b2c8fd5d8
Timestamp: 1729417693 Timestamp [UCT]: 2024-10-20 09:48:13 Age [y:d:h:m:s]: 00:034:22:08:20
Block: 1135619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24931 RingCT/type: yes/0
Extra: 01acb680c18f98243c5f7459592a99f2a681e3281774ace881a9d07b3b2c8fd5d8021100000009aa787773000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d40a4b927583570bcf663213a8ac2e70e348e5fe69528af3e48fad426d5880bc 0.600000000000 1618958 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": 1135629, "vin": [ { "gen": { "height": 1135619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d40a4b927583570bcf663213a8ac2e70e348e5fe69528af3e48fad426d5880bc" } } ], "extra": [ 1, 172, 182, 128, 193, 143, 152, 36, 60, 95, 116, 89, 89, 42, 153, 242, 166, 129, 227, 40, 23, 116, 172, 232, 129, 169, 208, 123, 59, 44, 143, 213, 216, 2, 17, 0, 0, 0, 9, 170, 120, 119, 115, 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