Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364a868e0fc8842f5433a0ac47111bf7fd0f6409337f1e1df6637105d1d8a9d9

Tx prefix hash: 14b330fe7f8577475996c789ffc11c176bb14c42ff14a5c2ff3ffef5450995cf
Tx public key: 8106182d130d36a6e87318de2a7e661eb83b7a8a498fca7532caf1ed33248a11
Timestamp: 1635340784 Timestamp [UCT]: 2021-10-27 13:19:44 Age [y:d:h:m:s]: 04:005:01:31:16
Block: 361557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1040440 RingCT/type: yes/0
Extra: 018106182d130d36a6e87318de2a7e661eb83b7a8a498fca7532caf1ed33248a1102110000000c328bb496000000000000000000

1 output(s) for total of 38.905587354000 dcy

stealth address amount amount idx
00: f86738a12408fe08aa273bccc18f67e297c5b3fdb0dc0fc22b7c626ec4f6150d 38.905587354000 735539 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": 361567, "vin": [ { "gen": { "height": 361557 } } ], "vout": [ { "amount": 38905587354, "target": { "key": "f86738a12408fe08aa273bccc18f67e297c5b3fdb0dc0fc22b7c626ec4f6150d" } } ], "extra": [ 1, 129, 6, 24, 45, 19, 13, 54, 166, 232, 115, 24, 222, 42, 126, 102, 30, 184, 59, 122, 138, 73, 143, 202, 117, 50, 202, 241, 237, 51, 36, 138, 17, 2, 17, 0, 0, 0, 12, 50, 139, 180, 150, 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