Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 904d4610fe7c84ffd0a523b66e54ea3878ce15141702f1f7341f50d27c7060df

Tx prefix hash: 92306c5427de085f794c25c50371ea7571242347ac881edfd1678ab49dd2a8b4
Tx public key: 03efe5789d011c750d66b441cb351f4e84ddb54fba1005c9d2b2f46909827796
Timestamp: 1671682846 Timestamp [UCT]: 2022-12-22 04:20:46 Age [y:d:h:m:s]: 02:115:04:04:07
Block: 657866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604003 RingCT/type: yes/0
Extra: 0103efe5789d011c750d66b441cb351f4e84ddb54fba1005c9d2b2f46909827796021100000003e6d27f9c000000000000000000

1 output(s) for total of 4.057110383000 dcy

stealth address amount amount idx
00: 5fe8b0c5852ea3c6b4a18f4b4186b94535c0af82be23c1e779332d5227a61a61 4.057110383000 1098519 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": 657876, "vin": [ { "gen": { "height": 657866 } } ], "vout": [ { "amount": 4057110383, "target": { "key": "5fe8b0c5852ea3c6b4a18f4b4186b94535c0af82be23c1e779332d5227a61a61" } } ], "extra": [ 1, 3, 239, 229, 120, 157, 1, 28, 117, 13, 102, 180, 65, 203, 53, 31, 78, 132, 221, 181, 79, 186, 16, 5, 201, 210, 178, 244, 105, 9, 130, 119, 150, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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