Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2b8e799efc3450f18d78f540a26b7d027aaaaacf97bcbe26cdf6d4d319094b1

Tx prefix hash: 2da799dc33fd19bb0e565849652d71be5c5a128bdbce5f61279af58526d37749
Tx public key: acfc74a83a767e94d6a3a14d2dd51d81847136db8bcde7758d37d9e9bbb8aed9
Timestamp: 1672958983 Timestamp [UCT]: 2023-01-05 22:49:43 Age [y:d:h:m:s]: 02:140:12:31:39
Block: 668427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622155 RingCT/type: yes/0
Extra: 01acfc74a83a767e94d6a3a14d2dd51d81847136db8bcde7758d37d9e9bbb8aed902110000000252542ceb000000000000000000

1 output(s) for total of 3.743034510000 dcy

stealth address amount amount idx
00: e4a675f0fbff365bd65b22bebd8a9e7b59885f8f31f51538c56e985576b6d98b 3.743034510000 1109674 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": 668437, "vin": [ { "gen": { "height": 668427 } } ], "vout": [ { "amount": 3743034510, "target": { "key": "e4a675f0fbff365bd65b22bebd8a9e7b59885f8f31f51538c56e985576b6d98b" } } ], "extra": [ 1, 172, 252, 116, 168, 58, 118, 126, 148, 214, 163, 161, 77, 45, 213, 29, 129, 132, 113, 54, 219, 139, 205, 231, 117, 141, 55, 217, 233, 187, 184, 174, 217, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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