Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14efa620a2eafb923d8bddb2ed6af98edf1026fc7e280956e266a05ca5332d2b

Tx prefix hash: a889659a76a5cac9c7430a3750e197d3214fabf905b106d690d91aabbbf667c7
Tx public key: fddd5e90c48be795e2cce8f2f76f286f527c5344984b22efa179b8b6593e37f4
Timestamp: 1713896934 Timestamp [UCT]: 2024-04-23 18:28:54 Age [y:d:h:m:s]: 00:261:11:09:54
Block: 1006955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187149 RingCT/type: yes/0
Extra: 01fddd5e90c48be795e2cce8f2f76f286f527c5344984b22efa179b8b6593e37f40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fba4c409ea2c810300920eaeffe4a4e48fe8a44eb9c7db46cab6ac50120ffd1 0.600000000000 1468153 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": 1006965, "vin": [ { "gen": { "height": 1006955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fba4c409ea2c810300920eaeffe4a4e48fe8a44eb9c7db46cab6ac50120ffd1" } } ], "extra": [ 1, 253, 221, 94, 144, 196, 139, 231, 149, 226, 204, 232, 242, 247, 111, 40, 111, 82, 124, 83, 68, 152, 75, 34, 239, 161, 121, 184, 182, 89, 62, 55, 244, 2, 17, 0, 0, 0, 4, 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