Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e36f323e03f03a294259150e347d34aa52f1448af875e756e5d14e216c24111e

Tx prefix hash: 5104b5df51fffdeee281c8cf3bbd038a4649e35abf3305daa1adbddc9ec0c35d
Tx public key: 0f48fd6738b8ba4016ace9d61eeca0b06af1425348c5ddf9aaef581df9afee63
Timestamp: 1726201854 Timestamp [UCT]: 2024-09-13 04:30:54 Age [y:d:h:m:s]: 00:209:11:05:36
Block: 1108965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149543 RingCT/type: yes/0
Extra: 010f48fd6738b8ba4016ace9d61eeca0b06af1425348c5ddf9aaef581df9afee6302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8edc64b44a0f7cad71196906d47576fec5370b2c8f9afb28bf479ad14b17ecd 0.600000000000 1587050 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": 1108975, "vin": [ { "gen": { "height": 1108965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8edc64b44a0f7cad71196906d47576fec5370b2c8f9afb28bf479ad14b17ecd" } } ], "extra": [ 1, 15, 72, 253, 103, 56, 184, 186, 64, 22, 172, 233, 214, 30, 236, 160, 176, 106, 241, 66, 83, 72, 197, 221, 249, 170, 239, 88, 29, 249, 175, 238, 99, 2, 17, 0, 0, 0, 1, 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