Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe8b15780021d44db0485a58d2cd00e9b5b9b4d54ce520bb68d1a3f4a7d90e5

Tx prefix hash: 471982dcb17f4f6b9ed32def8c4e15a3d2c8b719705f5e126d317e61b295b796
Tx public key: 4fbfda5049b54d2a9c11bbaa12158536b736e6ae9db60e467d50838217b2bbdf
Timestamp: 1649732001 Timestamp [UCT]: 2022-04-12 02:53:21 Age [y:d:h:m:s]: 02:233:10:40:27
Block: 478310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686707 RingCT/type: yes/0
Extra: 014fbfda5049b54d2a9c11bbaa12158536b736e6ae9db60e467d50838217b2bbdf021100000001d3fcec30000000000000000000

1 output(s) for total of 15.964695936000 dcy

stealth address amount amount idx
00: a934b3d8375487f06b8af71ec8c859e65da10b2a7d85e444a92224245e5ac9c6 15.964695936000 899055 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": 478320, "vin": [ { "gen": { "height": 478310 } } ], "vout": [ { "amount": 15964695936, "target": { "key": "a934b3d8375487f06b8af71ec8c859e65da10b2a7d85e444a92224245e5ac9c6" } } ], "extra": [ 1, 79, 191, 218, 80, 73, 181, 77, 42, 156, 17, 187, 170, 18, 21, 133, 54, 183, 54, 230, 174, 157, 182, 14, 70, 125, 80, 131, 130, 23, 178, 187, 223, 2, 17, 0, 0, 0, 1, 211, 252, 236, 48, 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