Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4473f1488cc726654db9372af9b54dd4fe9cdf640c2a6ada05617451f8a88bcc

Tx prefix hash: 1cb16379b7254d8b6796318ab265703421ca768bfc9affef15eb40b8d886cdf3
Tx public key: a20a87c369206728a66c78ab0c39a2c745f10fa059f1af6304e283bff8b6b5ea
Timestamp: 1711792839 Timestamp [UCT]: 2024-03-30 10:00:39 Age [y:d:h:m:s]: 01:076:06:47:50
Block: 989538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315424 RingCT/type: yes/0
Extra: 01a20a87c369206728a66c78ab0c39a2c745f10fa059f1af6304e283bff8b6b5ea0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a57de75cb2d2215a5f9e72e950d483f656bc20fb46c34cb752e3c2a9eb3e2e1 0.600000000000 1449837 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": 989548, "vin": [ { "gen": { "height": 989538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a57de75cb2d2215a5f9e72e950d483f656bc20fb46c34cb752e3c2a9eb3e2e1" } } ], "extra": [ 1, 162, 10, 135, 195, 105, 32, 103, 40, 166, 108, 120, 171, 12, 57, 162, 199, 69, 241, 15, 160, 89, 241, 175, 99, 4, 226, 131, 191, 248, 182, 181, 234, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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