Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae09492d7bdbaa04affc3b52e21cb1b5ac49ad3a014daca5516e9155c9dfb83d

Tx prefix hash: aae2dae9c3baab2b7d469e97566cd3500dc413eb4a0b7645ebd65f80846a7f96
Tx public key: 3e07e79f92cb77feb87771933dfce3d649d8179b9b1479656718b5eb8de62f1b
Timestamp: 1731314155 Timestamp [UCT]: 2024-11-11 08:35:55 Age [y:d:h:m:s]: 00:126:02:31:06
Block: 1151268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89963 RingCT/type: yes/0
Extra: 013e07e79f92cb77feb87771933dfce3d649d8179b9b1479656718b5eb8de62f1b02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d248264c3e70bcaf62ed083571617450a8e5e6b733a9b86931121eaf5947556 0.600000000000 1636765 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": 1151278, "vin": [ { "gen": { "height": 1151268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d248264c3e70bcaf62ed083571617450a8e5e6b733a9b86931121eaf5947556" } } ], "extra": [ 1, 62, 7, 231, 159, 146, 203, 119, 254, 184, 119, 113, 147, 61, 252, 227, 214, 73, 216, 23, 155, 155, 20, 121, 101, 103, 24, 181, 235, 141, 230, 47, 27, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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