Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b0f87e320a170340972babb735ad1662a5f5b8f99e928ce0b7fedb585a691fc

Tx prefix hash: 3c0a3477bb0f84e2d7f7c258077efdaed92717e9c47969af57693478b50fd2c3
Tx public key: 887d22d07b8a9eb1dc220497972064070acca9e5f770bf6ecd4b8013e2751b9c
Timestamp: 1579871175 Timestamp [UCT]: 2020-01-24 13:06:15 Age [y:d:h:m:s]: 05:107:23:09:06
Block: 51809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1228054 RingCT/type: yes/0
Extra: 01887d22d07b8a9eb1dc220497972064070acca9e5f770bf6ecd4b8013e2751b9c0211000000078a2ee0d9000000000000000000

1 output(s) for total of 413.367288785000 dcy

stealth address amount amount idx
00: 5ceb5e9c926a6e9bcf43c4b11b3760dcc86154575fae8e7811e2ccf670c9d44e 413.367288785000 96097 of 0

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": 51819, "vin": [ { "gen": { "height": 51809 } } ], "vout": [ { "amount": 413367288785, "target": { "key": "5ceb5e9c926a6e9bcf43c4b11b3760dcc86154575fae8e7811e2ccf670c9d44e" } } ], "extra": [ 1, 136, 125, 34, 208, 123, 138, 158, 177, 220, 34, 4, 151, 151, 32, 100, 7, 10, 204, 169, 229, 247, 112, 191, 110, 205, 75, 128, 19, 226, 117, 27, 156, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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