Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 325ba8be3223ffb99a0d22cea191d19d142e5ab24442c433283974dc83ca480d

Tx prefix hash: 7aa4e4a119f3f87b827dbd7b95eb279be5a68cc25e90ba7ef4b843748dbe92f9
Tx public key: 59e6dce6fbe73b37db6dc69c1df83073247b896f861cba96ea65a00ab9ab11e2
Timestamp: 1697369794 Timestamp [UCT]: 2023-10-15 11:36:34 Age [y:d:h:m:s]: 01:176:02:11:46
Block: 870146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386875 RingCT/type: yes/0
Extra: 0159e6dce6fbe73b37db6dc69c1df83073247b896f861cba96ea65a00ab9ab11e2021100000001faf35c9c000000000000000000

1 output(s) for total of 0.803239606000 dcy

stealth address amount amount idx
00: b28d1b21733598f9a54c0f55f8aa7a32d933b8ba6a5906ea85cbd94d00727f99 0.803239606000 1325019 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": 870156, "vin": [ { "gen": { "height": 870146 } } ], "vout": [ { "amount": 803239606, "target": { "key": "b28d1b21733598f9a54c0f55f8aa7a32d933b8ba6a5906ea85cbd94d00727f99" } } ], "extra": [ 1, 89, 230, 220, 230, 251, 231, 59, 55, 219, 109, 198, 156, 29, 248, 48, 115, 36, 123, 137, 111, 134, 28, 186, 150, 234, 101, 160, 10, 185, 171, 17, 226, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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