Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 713b5d2f75cfd103a5b6787a7ec061d4fe7eef397813103768be3030262ee251

Tx prefix hash: 6c56b2ca23e07f00db9979c0e21da24b4e18d7f44b7650c6ade7f4a4b29273d8
Tx public key: e2f2145a79bdca491c55cd8d74e10fd3433d1764ceb53fb3ac5403d04586943e
Timestamp: 1699321449 Timestamp [UCT]: 2023-11-07 01:44:09 Age [y:d:h:m:s]: 01:086:16:04:02
Block: 886125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323096 RingCT/type: yes/0
Extra: 01e2f2145a79bdca491c55cd8d74e10fd3433d1764ceb53fb3ac5403d04586943e02110000000233af99f4000000000000000000

1 output(s) for total of 0.711049820000 dcy

stealth address amount amount idx
00: 70da39abafed160cfba4db18c0b13a4896dfdba7ac32dbe10c6e26eeb89a2b79 0.711049820000 1341930 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": 886135, "vin": [ { "gen": { "height": 886125 } } ], "vout": [ { "amount": 711049820, "target": { "key": "70da39abafed160cfba4db18c0b13a4896dfdba7ac32dbe10c6e26eeb89a2b79" } } ], "extra": [ 1, 226, 242, 20, 90, 121, 189, 202, 73, 28, 85, 205, 141, 116, 225, 15, 211, 67, 61, 23, 100, 206, 181, 63, 179, 172, 84, 3, 208, 69, 134, 148, 62, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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