Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34384d1b09d9763155361500bc9a4cf5b2fdf01358147d6ed5f282f02615d978

Tx prefix hash: 39148cbfe4d5df2a087ebaafeeb587b227de92b73bc4728737f34b819d6d2a1e
Tx public key: c189ee3b8900c4b7d60ad355a07af8188f754eea24b25f59d45cb1aae573d173
Timestamp: 1729985766 Timestamp [UCT]: 2024-10-26 23:36:06 Age [y:d:h:m:s]: 00:028:08:25:04
Block: 1140316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20236 RingCT/type: yes/0
Extra: 01c189ee3b8900c4b7d60ad355a07af8188f754eea24b25f59d45cb1aae573d173021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55c9eed4f7ad2c53bbb92f396f70c47696414efed26a86ae9f1ee88770a2436c 0.600000000000 1624111 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": 1140326, "vin": [ { "gen": { "height": 1140316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55c9eed4f7ad2c53bbb92f396f70c47696414efed26a86ae9f1ee88770a2436c" } } ], "extra": [ 1, 193, 137, 238, 59, 137, 0, 196, 183, 214, 10, 211, 85, 160, 122, 248, 24, 143, 117, 78, 234, 36, 178, 95, 89, 212, 92, 177, 170, 229, 115, 209, 115, 2, 17, 0, 0, 0, 1, 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