Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec714fae84fc92a9874c228508e80dec5e4d46a55b799277b4b1c5c68e913de5

Tx prefix hash: 0129bb71e8e158acd292c8ef006b2e0f79a24576f64c133b50b307435eb61fb3
Tx public key: 2fae1b18eba00a99ee33d6c6b2b1e57496597902cb38ac2133695976af56a9db
Timestamp: 1721439672 Timestamp [UCT]: 2024-07-20 01:41:12 Age [y:d:h:m:s]: 00:252:07:23:59
Block: 1069533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180199 RingCT/type: yes/0
Extra: 012fae1b18eba00a99ee33d6c6b2b1e57496597902cb38ac2133695976af56a9db021100000001162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eb33513ffb053fee25a16aa37d7fd64032db5c4b874c00bc92a29c493e3ca98 0.600000000000 1540986 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": 1069543, "vin": [ { "gen": { "height": 1069533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eb33513ffb053fee25a16aa37d7fd64032db5c4b874c00bc92a29c493e3ca98" } } ], "extra": [ 1, 47, 174, 27, 24, 235, 160, 10, 153, 238, 51, 214, 198, 178, 177, 229, 116, 150, 89, 121, 2, 203, 56, 172, 33, 51, 105, 89, 118, 175, 86, 169, 219, 2, 17, 0, 0, 0, 1, 22, 38, 19, 170, 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